Well Identification
Every report type needs to identify its well. The reference payloads in this section are the shapes Fusion's shared mappings read today. They come from production integrations (most are WellView-style fields). If you can send these field names, Corva can attach your feed to an existing mapping. If your field names differ, send them as they are and Corva builds a mapping during onboarding. All values are illustrative.
How Fusion finds the well
Fusion looks for the well in this order and stops at the first identifier that matches:
- Corva asset ID (if you have it)
- API / UWI number
- Your own well ID (
customer_well_id, for example WellViewidwell) - Exact well name
- Alternative well names set up on the Corva asset
If more than one Corva asset matches (for example an original hole and its sidetrack), Fusion narrows the matches by the exact wellbore name, then by the report date against the rig-up and rig-release window.
Send wellbore_name with every report and keep it consistent with the wellbore name in Corva (for example Original Hole, Sidetrack 1). A missing or different wellbore name is the most common reason data lands on the wrong wellbore.
Accepted identifier fields
| Identifier | Field names Fusion's shared mappings already accept |
|---|---|
| API / UWI | wellida, uwi, api_no, apinumber |
| Your well ID | idwell, well_id, customer_well_id |
| Well name | wellname, well_name |
| Wellbore name | wellbore_name |
| Rig | rig_number, rig_name (optional; helps with rig-based matching) |